Bentley Automation Service Help

Creating and Editing Destination Profiles

A destination profile, or destination folder profile, is a template that defines where in ProjectWise the files that get created by a job will be stored.

When creating a job, each type of i-model you select to create has a preconfigured destination profile assigned to it by default. You can use the default profiles as is, you can edit them, or you can create your own profiles.

Destination Profiles for Intermediate Files

Use the steps below to create or edit a destination profile to be used for intermediate files.

  1. Begin to edit or create an i-model publishing job.
  2. On the iCS for i-models tab of the Job Builder dialog, turn on Create intermediate files.
  3. Click the ... button next to the list of Intermediate file destination profiles.

    The Output Destination Folder Profile Manager dialog opens. There is one delivered destination profile for intermediate files, called Default intermediate output destination folder.

  4. To create a profile, click the Add Profile icon.

    or

    To edit a profile, select a profile in the list and click the Set Profile Properties icon.

    The rest of the steps assume you are creating a profile. The controls in the Create and Edit dialogs are the same.

    The Create New Intermediate File Output Destination Folder Profile dialog opens.

  5. In the Name field, enter a name for the profile.

    This name will be added to the list of Intermediate file destination profiles on the iCS for i-models tab of the Job Builder dialog.

  6. In the Description field, enter a description of the profile.
  7. In the Destination Folder list, select where intermediate files will be stored:
    • source file folder - Stores intermediate files in the same folder as the source files they were created from. If an intermediate file with the same name already exists in this folder it will be overwritten.
    • relative folder from source file - Stores intermediate files in a folder under the source file folder called Intermediate files. This folder will be created as needed if it does not exist. If an intermediate file with the same name already exists in this folder it will be overwritten.
  8. If you want intermediate files to have the same (or some of the same) attribute values as the source documents they were created from, you can configure this by clicking Attribute Mapping.

    See Attribute Mapping Dialog .

  9. Click OK.

    The new profile is added to the Output Destination Folder Profile Manager dialog.

Destination Profiles for Packages and i-models

Use the steps below to create or edit a destination profile that can be used for either package files or i-model files.

  1. Begin to edit or create an i-model publishing job.
  2. On the iCS for i-models tab of the Job Builder dialog, do one of the following:

    Turn on Create a package file and click the ... button next to the list of Package destination profiles.

    or

    Turn on Create an i-model (.imodel) file and click the ... button next to the list of i-model destination profiles.

    The Output Destination Folder Profile Manager dialog opens. The list of available destination profiles is the same for packages and i-models.

    There are three delivered destination profiles that you can use for packages and i-models:

    • Default i-model output destination folder (this profile is selected as the default destination for i-models on the iCS for i-models tab)
    • Default package output destination folder (this profile is selected as the default destination for packages on the iCS for i-models tab)
    • Default transformed output destination folder
  3. To create a profile, click the Add Profile icon.

    or

    To edit a profile, select a profile in the list and click the Set Profile Properties icon.

    The rest of the steps assume you are creating a profile. The controls in the Create and Edit dialogs are the same.

    The Create New Output Destination Folder Profile dialog opens.

  4. In the Name field, enter a name for the profile.
  5. In the Description field, enter a description of the profile.
  6. From the Destination Folder list, select where packages or i-models will be stored:
    • relative folder from parent work area — Stores packages or i-models in a folder relative to a project. The system first searches up the directory tree until it locates a project. If it locates a project, it uses the string specified in the Relative Path field to determine where to place the packages or i-models. If a project is not found, the system behaves according to the relative folder from source file setting.
    • relative folder from source file — Stores packages or i-models in a folder relative to the source file folder. The system uses the string specified in the relative path field to determine where to place the packages or i-models. To place packages or i-models in a folder level to the parent folder, specify " ..\folder_name " for the relative path.
    • source file folder — Stores packages or i-models in the same folder as the source files they were created from.
    • specified folder — Stores packages or i-models in the datasource and folder specified in the Datasource and Folder fields.
  7. Set the options for the destination folder (the options available depend on what you select in the Destination Folder list):
    SettingDescription
    Relative Path (available when Destination Folder is set to relative folder from parent work area or relative folder from source file)

    This field lets you enter a string that defines a folder relative to the source file folder or a project. The system uses the string specified in this field to determine where to place the output. To place the output in a folder on the same level as the parent folder, specify " ..\folder_name " for the relative path. Click the Add Symbol button to add a ProjectWise or system variable to define the relative folder path or name.

    Datasource (available when Destination Folder is set to specified folder)

    Sets the datasource where the output will be stored. By default, this field is set to the same datasource that the source files come from. Click the Change button if you want to store the output in another datasource. Click the Revert button if you change the datasource and then decide you want to switch back to the original datasource.

    Folder (available when Destination Folder is set to specified folder)

    Sets the folder in the specified datasource where the output will be stored. Click the Browse button to browse to and select the folder you want. You can also click in the field and enter or edit the path to the destination folder. If you are typing the folder name, it must be a fully qualified ProjectWise URL. You can also click the Add Symbol button to add a ProjectWise or system variable to the field, in order to define the path to the destination folder, or to define the destination folder name itself.

    Create folder if it does not exist (available when Destination Folder is set to relative folder from parent work area, relative folder from source file, or specified folder)

    Turn this setting on if you want to allow the destination folder to be created if needed when the job is run. If this setting is off and the specified destination folder does not exist, the job will fail.

    Turning on this option also enables the following settings:

    • Environment — Lets you select which environment in the selected datasource to assign to the newly created destination folder. By default, the destination folder’s environment will be set to the same environment of the parent folder or project. If you do not want to assign an environment to the newly created destination folder, select the none option.
    • Storage — Lets you select which storage area in the selected datasource this newly created destination folder will use. By default, the destination folder’s storage area will be set to the same storage area of the parent folder or project.
    If file name is not unique in destination folder These options specify what should be done if the job creates a file with the same name as a file that already exists in the destination folder.
    • Overwrite file — If selected, documents having the same file name will be overwritten.
    • Create new version of file — If selected, and the job you run tries to send documents to the destination folder and there are already documents having the same file name in that folder (from a previous job, for example), then a new version of the document will be created.
    • Delete existing duplicate files and versions when appropriate — If on, all existing documents in the destination folder having the same file name as the file to be distributed are deleted prior to creating the destination document, if the source file that corresponds to that destination document is the oldest in its version series.
    Note: The first document in a version series is typically denoted with sequence zero, but that does not have to be the case. If you delete the original sequence zero document, then the next oldest document will become the first document in the version series — even though it retains its greater-than-zero sequence number.
    Mirror source datasource folder structure (available when Destination Folder is set to relative folder from parent work area, relative folder from source file, or specified folder)

    If on, the directory structure of the input set will be replicated in the target folder, and renditions will be distributed to their respective folder in the mirrored directory structure.

  8. If you want packages or i-models to have the same (or some of the same) attribute values as the source documents they were created from, you can configure this by clicking Attribute Mapping.

    See Attribute Mapping Dialog .

  9. Click OK.

    The new profile is added to the Output Destination Folder Profile Manager dialog, and it is also added to the list of Package destination and i-model destination profiles on the iCS for i-models tab of the Job Builder dialog.

Parent topic: i-model Publishing Workflow